Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace calls to performance API with LAMP data (Version 4.1) #976

Merged
merged 17 commits into from
May 12, 2024

Conversation

devinmatte
Copy link
Member

@devinmatte devinmatte commented Apr 8, 2024

Motivation

Replace all calls to the performance API with LAMP data, and gobble as fallback

Changes

  • Removes calls to the performance API
  • Fetches LAMP csvs properly
  • Uses v3 Alerts when available
  • Bumps release version to v4.1!
  • Runs npm update to do some package cleanup and updating

Depends on

Do not consider merging until we've finished these issues

Testing Instructions

Go to beta, compare results to prod

@github-actions github-actions bot added the backend Change to backend code label Apr 8, 2024
@devinmatte devinmatte self-assigned this Apr 8, 2024
@github-actions github-actions bot added the dependencies Changes to dependencies label Apr 14, 2024
@devinmatte devinmatte changed the title Replace calls to performance API with LAMP data Replace calls to performance API with LAMP data (Version 4.1) Apr 14, 2024
@github-actions github-actions bot added ci/cd Affects or Updates CI/CD documentation Improvements or additions to documentation labels Apr 18, 2024
@devinmatte devinmatte marked this pull request as ready for review April 18, 2024 23:38
"S3 Headway Fetching": (
lambda: "2020-11-07T10:33:40"
in json.dumps(data_funcs.headways(date(year=2020, month=11, day=7), ["70061"]))
),
"Performance API Check": (
Copy link

@salil-khanna salil-khanna May 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Briefly read architecture docs, but based on this PR, I'm assuming that LAMP data is held in a separate repo through an s3 bucket? So the S3 Headway Fetching thats done above covers the check for LAMP as well?

Also why did the MbtaPerformanceAPI need a check but not MbtaAPIV3/V2?

Copy link
Member Author

@devinmatte devinmatte May 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LAMP data is processed through mbta-performance and stored in s3. We read from s3 here, so yes. That check is sufficient for both

We don't have any checks for the v3 api mostly because we haven't relied on the v3 api for much in the app. Now we only use it to show current accessibility alerts, so we could add a check here, just haven't

Copy link
Contributor

@skaplan-dev skaplan-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@github-actions github-actions bot added the frontend Change to frontend code label May 12, 2024
@devinmatte devinmatte merged commit f2a9553 into main May 12, 2024
4 checks passed
@devinmatte devinmatte deleted the use-lamp-data branch May 12, 2024 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Change to backend code ci/cd Affects or Updates CI/CD dependencies Changes to dependencies documentation Improvements or additions to documentation frontend Change to frontend code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants